Secure transmission-pairing database system

ABSTRACT

A transmission pairing system may include a transmission pairing stored in a secure database. The system may generate a transmission pairing by receiving a selection of a destination for the secure information from the secure database and determining a transmission type corresponding to the selected destination. The system may populate a list of available sources of the secure information based on the transmission type. A selected source may be received and paired with the selected destination to generate the transmission pairing. The transmission pairing may be used to initiate an electronic transmission based on a parameter that is modifiable to determine the secure information transmitted from the source to the destination.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.15/154,230 filed May 13, 2016 and titled “Secure Transmission-PairingDatabase System,” which claims priority to U.S. Provisional ApplicationSer. No. 62/160,941, filed May 13, 2015 and titled “Web-Based SecuredTransmission Pairing System,” the contents of both of which areincorporated herein by reference.

TECHNICAL FIELD

The present disclosure relates to secure database systems, and moreparticularly, though not necessarily exclusively, to using storedtransmission pairings with a modifiable parameter to initiate electronictransmissions of secure information.

BACKGROUND

Some systems may be accessible via a network, such as the Internet, tostructure and implement transmissions of information securely from asource to a destination. The transmission details may be stored and usedto execute additional transmissions of an identical type. But, forfuture transmissions that are not identical to the stored transmission,such systems must recommence the process of structuring and implementingthe transmission, regardless of the similarities between thetransmissions.

SUMMARY

In some aspects, a system may include a secure database having (1) aplurality of source identifiers corresponding to sources from whichsecure information is electronically transmittable and (2) a pluralityof destination identifiers corresponding to destinations to which thesecure information is electronically transmittable. The plurality ofsource identifiers may be linked with a user identifier in the securedatabase. The user identifier may correspond to a user of a user device.The secure information may include user information that is accessibleby the user from the user device subsequent to an authentication of theuser. The system may also include a processor communicatively coupled tothe secure database. The system may also include a memorycommunicatively coupled to the processor and including instructions thatare executable by the processor for causing the processor to generate afirst user interface displayable on the user device communicativelycoupled to the processor via a network. The first user interface mayinclude a list of available destinations corresponding to a set ofdestination identifiers of the plurality of destination identifiers. Theinstructions may also be executable by the processor for causing theprocessor to receive, from the user device via the network, a firstselection corresponding to a destination from the list of availabledestinations. The instructions may also be executable by the processorfor causing the processor to determine a transmission type based on thedestination. The instructions may also be executable by the processorfor causing the processor to generate a second user interfacedisplayable on the user device and including a list of available sourcescorresponding to a set of source identifiers of the plurality of sourceidentifiers. The set of source identifiers may correspond to thetransmission type. The instructions may also be executable by theprocessor for causing the processor to receive, from the user device viathe network, a second selection corresponding to a source from the listof available destinations. The instructions may also be executable bythe processor for causing the processor to generate a transmissionpairing including the source and the destination by linking a sourceidentifier corresponding to the source and a destination identifiercorresponding to the destination in the secure database. Theinstructions may also be executable by the processor for causing theprocessor to link the transmission pairing with the user identifier inthe secure database. The instructions may also be executable by theprocessor for causing the processor to generate a third user interfacedisplayable on the user device and including a selection optioncorresponding to the transmission pairing and selectable by the userdevice to initiate a transmission process in which the secureinformation is electronically transmitted from the source to thedestination to modify source information and destination informationbased on a parameter received from the user via the user devicesubsequent to a selection of the selection option.

In some aspects, a method may include receiving, from a user via a userdevice, a request to generate a transmission pairing. The method mayalso include displaying a first list of a plurality of availabledestinations for the transmission pairing. The plurality of availabledestinations may correspond to destinations to which secure informationis electronically transmittable. The method may also include receiving afirst selection corresponding to a destination from the first list. Themethod may also include determining a transmission type based on thedestination. The method may also include displaying a second list of aplurality of available sources corresponding to the transmission type.The plurality of available sources may include sources from which secureinformation is electronically transmittable. The method may also includereceiving a second selection corresponding to a source from the secondlist. The method may also include generating the transmission pairingincluding the source and the destination by linking a source identifiercorresponding to the source and a destination identifier correspondingto the destination in a secure database. The method may also includelinking the transmission pairing with a user identifier in the securedatabase, the user identifier corresponding to the user. The method mayalso include displaying a selection option corresponding to thetransmission pairing and selectable by the user device to initiate atransmission process in which the secure information is electronicallytransmitted from the source to the destination to modify sourceinformation and destination information based on a parameter receivedfrom the user via the user device subsequent to a selection of theselection option.

In some aspects, a system may include a secure database including aplurality of memory locations. Each memory location in the plurality ofmemory locations may be linked to at least one other memory location inthe plurality of memory locations. The plurality of memory locations mayinclude a plurality of user identifiers. The plurality of memorylocations may also include a plurality of transmission pairings. Eachtransmission pairing of the plurality of transmission pairings mayinclude a source identifier corresponding to a source linked with adestination identifier corresponding to a destination, the source havingsource information from which secure information is electronicallytransmittable. The destination may have destination information to whichthe secure information is electronically transmittable, the secureinformation including user information that is accessible by a user froma user device subsequent to an authentication of the user. The pluralityof memory locations may also include authentication informationcorresponding to a plurality of users and including user authenticationinformation for authenticating each user of the plurality of users toaccess the secure information via user devices communicatively coupledto the secure database by a network. The system may also include amemory communicatively coupled to the secure database and includinginstructions that are executable by a processor for causing theprocessor to generate a first user interface displaying at least onetransmission pairing of the plurality of transmission pairings and atleast one selection option corresponding to the at least onetransmission pairing. The at least one transmission pairing may includea first source and a first destination, where a first source identifiercorresponding to the first source may be linked to a first destinationidentifier corresponding to the first destination in the securedatabase. The at least one selection option may be selectable by theuser via the user device to transmit a request signal corresponding to arequest to initiate an electronic transmission of the secure informationfrom the first source to the first destination. The instructions mayalso be executable by a processor for causing the processor to generate,in response to receiving the request signal, a second user interfaceincluding the first source, the first destination, and a first inputoption selectable by the user via the user device to input a parameter.The instructions may also be executable by a processor for causing theprocessor to initiate the electronic transmission of the secureinformation from the first source to the first destination based on theparameter.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram depicting a network environment including atransmission pairing system according to some aspects of the presentdisclosure.

FIG. 2 is a block diagram depicting memory locations in a securedatabase of the transmission pairing system according to some aspects ofthe present disclosure.

FIG. 3 is a flow chart of a process for generating a transmissionpairing according to some aspects of the present disclosure.

FIG. 4 is an example of a user interface displaying transmissionpairings according to some aspects of the present disclosure.

FIG. 5 is an example of a user interface for generating a transmissionpairing according to some aspects of the present disclosure.

FIG. 6 is an example of a user interface displaying the transmissionpairing of FIG. 5 according to some aspects of the present disclosure.

FIG. 7 is an example of a user interface displaying an executedtransmission with a selection option to generate a transmission pairingaccording to some aspects of the present disclosure.

FIG. 8 is a flow chart of a process for implementing a transmissionusing a transmission pairing according to some aspects of the presentdisclosure.

FIG. 9 is an example of a user interface for implementing a transmissionusing a transmission pairing according to some aspects of the presentdisclosure.

FIG. 10 is an example of a user interface confirming the transmission ofFIG. 9 according to some aspects of the present disclosure.

DETAILED DESCRIPTION

Certain aspects and examples of the present disclosure relate to asecure database including a stored transmission pairing that may be usedto initiate a transmission of secure information from a source to adestination in a manner that modifies secure information correspondingto the source and the destination based on a modifiable parameter. Theparameter may be received from a user via a user device to determine thesecure information to be transmitted from the source to the destinationand define the parameters by which the secure information at the sourceand the destination be modified. In some aspects, a system may execute avalidation process to determine if the source is able to transmit thesecure information to the destination based on the parameter prior toinitiating the electronic transmission. For example, the system maydetermine if the secure information at the source is modifiable based onthe parameter.

The transmission pairing stored in the secure database may be generatedin response to a request by the user. In some aspects, the system maygenerate a user interface including a list of available destinations forthe transmission pairings. The destinations may correspond to accountsor other information stored in the secure database and available toreceive secure information. The system may determine the type oftransmission for the transmission pairing based on the type ofdestination selected by the user. For example, a destinationcorresponding to an account or other location managed by the user mayimplicate a first type of transmission while a destination correspondingto an account managed by a third party may implicate a second type oftransmission. The system may populate a list with sources correspondingto the determined transmission type and available for transmittingsecure information to the selected destination. Upon selection of asource from the list, the system may generate the transmission pairingby associating the source with the destination in the database. Thetransmission pairing may be associated with the user to allow the userto access the transmission pairing for initiating a transmission.

A system according to some aspects may provide quick initiation offrequent electronic transmissions of secure information while accountingfor important parameter changes that may exist each time thetransmission is initiated. Unlike current systems that may operate underan assumption that an electronic transmission between a source and adestination is identical each time it is initiated, the parameter may bemodified to initiate a unique transmission using the same transmissionpairing. The ability to modify an aspect of the transmission withoutrestructuring an entirely new transmission having the same source anddestination may reduce bandwidth on a network when completing frequenttransmission. Further, a transmission pairing according to some aspectsof the present disclosure may result in a significant amount of memorysaved in the database as a single transmission pairing for each user mayreplace multiple stored transmission pairings having the samesource-destination pairing, but slightly different parameterscorresponding to the secure information transmitted from the source tothe destination.

Various aspects of the present disclosure may be implemented in variousenvironments. FIG. 1 is a block diagram depicting a network environment100 including a transmission pairing system 102 according to someaspects of the present disclosure. The transmission pairing system 102is communicatively coupled to a user device 104 via a network 106, suchas the Internet. The transmission pairing system 102 includes a networkinterface 108 coupled to a processor 110 and a memory 112 via a bus. Thenetwork interface 108 may include a network card or other devicecommunicatively coupled to the network 106 to allow user devices, suchas the user device 104, to access the transmission pairing system 102for generating a transmission pairing and initiating transmissions usingthe transmission pairing. In some aspects, the network interface 108 maytransmit user interfaces generated by the processor 110 via the network106 to the user device 104.

The processor 110 may execute instructions stored in the memory 112 toperform the operations of the transmission pairing system 102. Theprocessor 110 may include a single processing device or multipleprocessing devices. Non-limiting examples of the processor 110 include afield-programmable gate array, an application-specific integratedcircuit (“ASIC”), and a microprocessor. The memory 112 includes astorage device that retains information when powered off. Non-limitingexamples of the memory 112 include electrically erasable andprogrammable read-only memory, a flash memory, or any other type ofnon-volatile memory.

In some examples, at least a portion of the memory 112 may include acomputer-readable medium from which the processor 110 can readinstructions of the memory 112. A computer-readable medium may includeelectrical, optical, magnetic, or other storage devices capable ofproviding the processor 110 with computer-readable instructions or otherprogram code. Non-limiting examples of a computer-readable mediuminclude magnetic disks, memory chips, read-only memory, random-accessmemory, an ASIC, a configured processor, optical storage, or any othermedium from which the processor 110 may read instructions. Theinstructions may include processor-specific instructions generated by acompiler or an interpreter from code written in any suitablecomputer-programming language, including, for example, C, C++, C#,COBOL, Java, etc.

The instructions in the memory 112 include pairing instructions 114. Thepairing instructions 114 may include instructions to cause the processor110 to generate a transmission pairing by linking sources anddestinations of secure information. The pairing instructions 114 mayalso include instructions to determine a transmission type based on thedestination of the generated pairing and to identify available sourcescorresponding to the transmission type. In some aspects, thetransmission type may include at least a Type-A transmission and aType-B transmission. In some examples, the Type-A transmissions maycorrespond to transmissions in which secure information is transmittedfrom a source to a destination, where the source and destination areboth held by a common owner. In a particular example, the source and thedestination may correspond to financial accounts held by the sameaccount holder. The transmission may relate to a transfer of monetaryinformation from the source to the destination. In other examples, theType-A transmissions may correspond to other types of transmissions,including, but not limited to, transmissions in which the source and thedestination are both of a similar type (e.g., individually held checkingaccounts). In some examples, the Type-B transmissions may correspond totransmissions in which the source and destination are held by differentowners, such as a payment transmission in which monetary information istransmitted from a source account held by a first entity or individualto a destination account held by a second entity or individual. In otheraspects, the Type-B transmissions may correspond to other types oftransmissions, including, but not limited to, transmissions betweendifferent types of accounts (e.g., an individual checking account to acorporate checking account). Although only two types of transmission aredescribed, the transmission pairing system 102 may initiate any numberof transmission types, including one. In some aspects, the pairinginstructions 114 may be executed by the processor 110 to generate one ormore user interfaces to allow a user of the user device 104 to generatea transmission pairing and to display one or more generated transmissionpairings on a display unit of the user device 104.

The memory 112 also includes Type-A instructions 116 and Type-Binstructions 118. The Type-A instructions 116 and the Type-Binstructions 118 may include instructions for initiating transmissionsof types A and B, respectively, in response to a user selection of thetransmission pairing from a user interface generated by the processor110 using the pairing instructions 114. In some aspects, the Type-Ainstructions 116 and the Type-B instructions 118 may cause the processor110 to transmit secure information from a source to a destination bymodifying information at the source and information at the destinationby a parameter selected by the user. In some aspects, the Type-Ainstructions 116 and the Type-B instructions may cause the processor 110to generate one or more user interfaces to allow a user to input theparameter for the transmission of secure information.

The transmission pairing system 102 also includes a secure database 120.The secure database 120 may include a single database or multipledatabases including information to facilitate the transmission of secureinformation from a source to a destination. In some aspects, securedatabase 120 may include source identifiers and destination identifiersthat may be linked together to generate transmission pairings 122. Thetransmission pairings 122 may be displayed on the user device 104 andselected to initiate a transmission of secure information from a sourceto a destination linked to the source. The secure database 120 alsoincludes pairing notes 124. The pairing notes 124 may includeinstructions, comments, textual memoranda, or other instructive notescorresponding to the transmission pairings 122. In some aspects, theuser interfaces generated by the pairing instructions 114 may allow auser to input text that may be stored in the secure database 120 andassociated, or otherwise linked, to a pairing 122 in the secure database120. Historical transmission data 126 and preferences 128 are alsoincluded in the secure database 120. The historical transmission data126 may include information corresponding to transmissions previouslyinitiated by a user. In some aspects, the historical transmission data126 may include sources and destinations of the previously initiatedtransmissions. The preferences 128 include user preferences for thedisplay of the transmission pairings 122. For example, the preferences128 may include an order in which the transmission pairings may bedisplayed on a user interface generated by the processor 110. In anotherexample, the preferences 128 may include user device information and auser's previously selected preferences on which user devices to displaywhich transmission pairings 122 (e.g., a first transmission pairingdisplayed on a first user device and a second transmission pairingdisplayed on a second user device).

The user device 104 may represent one or more user devicescommunicatively coupled to the transmission pairing system 102 via thenetwork 106. The user device 104 may be a computing device, such as alaptop, mobile phone, desktop computer, personal digital assistant,tablet, etc., that may display content in a web browser or other userinterface. The transmission pairing system may receive requests andcommands from the user device 104 via the network 106 and configure theuser interfaces to be provided to the user device 104 in response to therequests and commands.

FIG. 2 is a block diagram depicting memory locations in the securedatabase 120 of the transmission pairing system 102 according to someaspects of the present disclosure. The secure database 120 may link, orotherwise associate, information within each memory location tofacilitate generating the transmission pairings 122 and initiatingtransmissions based on the transmission pairings 122. In some aspects,the information within each location may be linked in or more indices inthe secure database 120. For example, an index may include one or morecolumns, each including information that is associated with otherinformation in the same column of the index. In additional andalternative aspects, the information may be linked using pointers,objects, or other means for associating information in the securedatabase 120. In some aspects, the information stored in the securedatabase 120 may be separated or partitioned by information type toallow the processor 110 of the transmission pairing system 102 of FIG. 1to query information based on a first type and use the links todetermine information of a second type linked to the first type ofinformation. Although the secure database 120 is depicted as a singledatabase in FIG. 2, the secure database 120 may include multipledatabases including associated memory locations.

User identifiers 200 are stored in the secure database 120 and includeinformation corresponding to an identity of an account holder, member,or other user of the transmission pairing system 102. In some aspects,the user identifiers 200 may include a unique set of alphanumericcharacters, such as an online banking (“OLB”) number assigned toaccountholders to distinguish holders of each account managed by afinancial institution. In other aspects, the user identifiers 200 mayinclude a unique set of alphanumeric characters provided by or issued toeach user, including, but not limited to, a social security number.

The secure database 120 also includes authentication information 202.The authentication information 202 may include information forauthenticating a user to access the secure database 120 to generate thetransmission pairings 122 and to view and transmit secure informationstored in the secure database 120. In some aspects, the authenticationinformation 202 may include information provided by the user, including,but not limited to, a username, password, social security number,passcode, or other authenticating information. In other aspects, theauthentication information 202 may include information provided to theuser, such as, but not limited to, a personal identification number(“PIN”). The authentication information 202 may be stored in the securedatabase 120 and compared with input from the user via the user device104 of FIG. 1 for a match to conclude that the user is authorized toview and transmit the secure information.

The secure database 120 also includes source identifiers 204 anddestination identifiers 206. In some aspects, the source identifiers 204may include account information, devices, locations or other identifiersof secure information at source, at least a portion of which may betransmitted to a destination. In some aspects, the accounts associatedwith the source identifiers 204 in the secure database 120 may be storedin a remote database. The destination identifiers 206 may includeaccount information, devices, locations, or other identifiers ofdestinations that may receive the secure information. For example, asource identifier 204 and a destination identifier 206 may correspond tofinancial account information. For example, the source identifier 204may include account numbers and routing numbers associated with theaccount. In some aspects, the source identifier 204 may also includebalance information corresponding to an amount of money available in thesource account. The destination identifier 206 may include accountnumbers and routing numbers. In some aspects, the accounts associatedwith the destination identifiers 206 in the secure database 120 may bestored in a remote database. A transmission from the source to thedestination may include transmitting monetary information from thesource to the destination. The value of the monetary information (e.g.,the amount of money transmitted) may be a parameter selected by the uservia the user device 104 and may cause secure source information andsecure destination information to be modified by the parameter. Forexample, the parameter may be a fifty-dollar value, and the balance ofthe source account may be deducted by fifty dollars while the balance ofthe destination account may be increased by fifty dollars.

The source and the destination may be included in a transmissionpairing. For example, a source identifier 204 and a destinationidentifier 206 may be linked in the secure database 120 to form atransmission pairing 122. In some aspects, the transmission pairing 122may include a copy of the source identifier 204 and the destinationidentifier 206 forming the transmission pairing. In other aspects, thetransmission pairings 122 may include links, objects, or otherreferences to the source identifiers 204 (or the source) and thedestination identifiers 206 (or the destination) forming thetransmission pairings 122. The secure database 120 also includes thehistorical transmission data 126 and the preferences 128 described inFIG. 2.

The transmission pairings 122 may be linked to the user identifiers 200to allow the user to access and view the appropriate transmissionpairings from the user device. For example, subsequent to authenticatingthe user, the transmission pairing system 102 of FIG. 1 may generate auser interface displaying the transmission pairings 122 linked to theuser identifier associated with the authentication information 202received from the user via the user device 104 of FIG. 1. The sourceidentifiers 204 and the destination identifiers 206 may be linked toform the transmission pairings 122. The source identifiers 204 and thedestination identifiers 206 may also be linked and stored as historicaltransmission data 126 subsequent to a transmission initiated by the userinvolving a source and a destination. The source identifiers 204 and thedestination identifiers 206 may also be linked to the user identifiers200 to allow the transmission pairing system 102 to generate a list ofavailable sources and available destinations for selection by the userto generate the transmission pairings 122. In some aspects, the sourceidentifiers 204 may be further linked with the user identifiers 200 toallow the user to access secure information in the source identifier 204for transmitting to a destination identifier 206.

The historical transmission data 126 may also be linked to one or moreof the transmission pairings 122 to allow the transmission pairingsystem 102 of FIG. 1 to generate a transmission pairing 122 using apreviously initiated transmission. The preferences 128 may be linked tothe user identifiers 200 to allow the transmission pairing system 102 todetermine the user's preferences for displaying the transmissionpairings 122 on the user device 104.

Generating a Transmission Pairing

FIG. 3 is a flow chart of a process for generating a transmissionpairing according to some aspects of the present disclosure. The processis described with respect to the network environment 100 of FIG. 1 andthe secure database 120 of FIGS. 1 and 2, although other implementationsare possible without departing from the scope of the present disclosure.

In block 300, a request is received from the user to generate atransmission pairing 122. The request may be received by thetransmission pairing system 102 from the user via the user device 104.In some aspects, the request may be received in response to a userselecting a selection option displayed on a user interface on the userdevice 104 corresponding to the request. Selecting the selection optionmay generate a request signal that is transmitted from the user device104 to the user device 104 to the transmission pairing system 102 viathe network 106 and processed by the processor 110.

In block 302, available destinations 206 are displayed. In some aspects,the processor 210 may generate a user interface including one or moreavailable destination 206 to which secure information may be transmittedby the user. The transmission pairing system 102 may display theavailable destinations for a selection by the user of a destination forthe transmission pairing. In some aspects, the transmission pairingsystem 102 may display the available destinations in the form of a list(e.g., a drop-down menu). The transmission pairing system 102 maydisplay a user interface that includes a webpage configured to displayone or more destinations and receive a selection corresponding to auser's selection of a destination from the available destinations. Theavailable destinations may be stored in the secure database 120 andretrieved by the transmission pairing system 102 subsequent to the userbeing authenticated by the transmission pairing system 102. In someaspects, the transmission pairing system 102 may not display all of theavailable destinations. For example, the transmission pairing system 102may display a portion of the available destinations with an option toview additional available destinations. This may prevent cluttering thelist with destinations that may be less likely for selection by theuser. For example, the transmission pairing system 102 may display onlyavailable destinations that a user has recently initiated atransmission. For example, destinations stored in the historicaltransmission data 126 and linked to the user identifier 200 of the usermay be displayed first followed by additional destinations 206. The usermay select the option to view other available destinations.

In block 304, the transmission pairing system 102 receives a selectionof a destination from the available destinations. The destinationselection may be received as an input in response to a selection of adestination from the available destinations displayed on a userinterface.

In block 306, the transmission pairing system 102 may determine atransmission type. The transmission type may be based on the selectionof the destination. In some aspects, the transmission type may bedetermined using the destination type. Certain types of destinations mayindicate that the transmission of secure information to the destinationsis of a particular type. For example, the destination selection receivedin block 304 may correspond to a destination previously linked to theuser identifier 200 of the user, indicating that the destination isowned or otherwise managed by the user. The ownership of the destinationby the user may indicate that the transmission of information from asource to the destination is of a Type-A corresponding to transmittingsecure information between commonly owned locations (e.g., a source anda destination both owned by the user). In another example, thedestination selection received in block 304 may correspond to adestination associated with a user identifier 200 of a third party(e.g., the destination is not owned or managed by the user). Theownership of the destination by a third party may indicate that thetransmission of information is of a Type-B that is different from aType-A transmission (e.g., a source and a destination owned by separateentities).

In response to identifying the transmission type, the transmissionpairing system 102 may determine a list of available sourcescorresponding to the type. For example, the transmission pairing system102 may determine sources available to transmit secure information tothe selected destination using a Type-A transmission upon determiningthat the destination selection corresponds to a Type-A transmission. Inanother example, the transmission pairing system 102 may determinesources available to transmit secure information to the selecteddestination using a Type-B transmission upon determining that thedestination selection corresponds to a Type-B transmission.

In block 308, the transmission pairing system 102 displays one or moresources available for a Type-A transmission in response to adetermination that the transmission is a Type-A transmission. In block310, the transmission pairing system 102 displays one or more sourcesavailable for a Type-B transmission in response to a determination thatthe transmission is a Type-B transmission. In some aspects, thetransmission pairing system 102 may generate a user interface to displaythe available sources on the user device 104. In some aspects, the userinterface may include a modified version of the user interfacedisplaying the available destinations in block 302. For example, theuser interface described in block 302 may be updated to include the listof available destinations and a second list (e.g., a second pull-downmenu) including the available sources. The available sources may includeselection options to allow the user to select a source for pairing withthe destination selected in block 304.

In block 310, the transmission pairing system 102 displays the availablesources. The transmission pairing system 102 may display a userinterface that includes a webpage configured to display one or moresources and receive an input or selection corresponding to a user'sselection of a source from the available sources. The user interface mayfurther include the selected destination (or a list of availabledestinations) displayed in addition to the available sources. In someexamples, the available sources may be displayed as a drop-down menu.

In block 312, the transmission pairing system 102 receives a selectionof a source. The source selection may be received in response to aselection of a source from available sources displayed on a userinterface.

In block 314, a transmission pairing is generated using the destinationselection received in block 304 and the source selection received inblock 312. The transmission pairing may be generated by the transmissionpairing system 102. Generating the transmission pairing may includeassociating or otherwise linking the selected source and the selecteddestination in the secure database 120. In some aspects, thetransmission pair may be stored separately from the sources 204 and thedestinations 206 in the secure database 120. In other aspects, thetransmission pair may include links, objects, or other references to thedestination and the source included in the transmission pairing. Thetransmission pairing may also be linked to the user identifier 200 ofthe user to allow the transmission pairing to be displayed on the userdevice subsequent to the user being authenticated to access the securedatabase 120. In some aspects, generating the transmission pairing mayalso include additional validations related to the selected destinationand selected source. For example, the transmission pairing system 102may verify that the destination and source still exist in the securedatabase or that other criteria for the transmissions pairing aresatisfied prior to storing the transmission pairing in the securedatabase 120.

In block 316, the transmission pairing system 102 displays thetransmission pairing. The transmission pairing system 102 may generate auser interface including the transmission pairing and a selection optioncorresponding to the selection that may be selected by the user toinitiate a transmission of secure information from the source receivedin block 312 to the destination received in block 304. In some aspects,the user interface may include a list of transmission pairingspreviously generated by the transmission pairing system 102. In someexamples, the transmission pairing or list of transmission pairings maybe displayed as a widget or button on a user interface.

In some aspects, the transmission pairing system 102 may generate apairing as described in block 314 from a previous transmission. Forexample, subsequent to receiving a request to generate a pairing asdescribed in block 300, the transmission pairing system 102 maydetermine that the request was transmitted in response to a userselection of a selection option displayed with a confirmation of aprevious transmission. In response to receiving the request from theselection option, the transmission pairing system 102 may generate atransmission pairing using the source and the destination of theprevious transmission as the source and destination for the transmissionpairing.

In some aspects, the transmission pairing system 102 may also allow aninstructive note to be linked to the transmission pairing. For example,the user interface generated in blocks 302, 308, or 310 may include aninput option that may be selected by the user via the user device toinput alphanumeric text that may be displayed with the transmissionpairing as described in block 316. In some aspects, the transmissionpairing system 102 may store the note with the pairing note 124 in thedatabase and associate it with the transmission pairings. In otheraspects, the transmission pairing system 102 may store the note with thetransmission pairings 122 themselves.

Illustrative Example of Transmission Pairings

FIG. 4 is an example of a user interface 400 displaying transmissionpairings 402, 404 according to some aspects of the present disclosure.In some aspects, the user interface may be generated by the transmissionpairing system 102 and transmitted to the user device 104 via thenetwork 106 for display on a display unit of the user device 104. Thetransmission pairings 402, 404 include a name of the destination towhich secure information may be transmitted using the transmissionpairings 402, 404. For example, the transmission pairing 402 indicatesthat it may be selected by the user to initiate a transmission to afinancial checking account. The transmission pairing 404 indicates thatit may be selected by the user to initiate a transmission to a sewerutility company's financial account. The user interface 400 alsoincludes a selection option 406, labeled “Add a Pairing,” that may beselected by the user via the user device to generate a new transmissionpairing. Selecting the selection option 406 may initiate the process ofFIG. 3.

FIG. 5 is an example of a user interface 500 for generating a newtransmission pairing according to some aspects of the presentdisclosure. The user interface 500 may be generated by the transmissionpairing system 102 in response to a selection of the selection option406 in FIG. 4. The user interface includes a drop-down menu 502including a list of available destinations that may be selected as thedestination for the transmission pairing. In some aspects, the list maybe generated as described in block 302 of FIG. 3. The user interfaceindicates that the selected destination is a garbage utility company.Based on the selection of the garbage utility company as thedestination, the transmission pairing system 102 may determine that thetransmission type corresponds to a payment. The transmission pairingsystem 102 may populate the drop-down menu 504 with a list of availablesources for a payment transmission. In some aspects, the list may begenerated as described in blocks 308, 310 of FIG. 3.

The user interface 500 also includes an input option 506 that may beselected by the user via the user device 104 to enter an instructivenote. The note includes alphanumeric text received from the user using akeyboard of the user device 104. The transmission pairing system 102 maystore the note entered in the input option 506 in the database andassociate it with the transmission pairing to allow the note to bedisplayed with the transmission pairing.

FIG. 6 is an example of a user interface 600 displaying the transmissionpairing of FIG. 5 according to some aspects of the present disclosure.The user interface 600 includes the transmission pairings 402, 404 ofFIG. 4 and an additional transmission pairing 602 for initiating atransmission between the source and the destination selected by the userfrom the user interface 500 of FIG. 5. The transmission pairing 602 alsoincludes the instructive note displayed with the transmission pairing602. Each of the transmission pairings 402, 404, 602 includes aselection option 604, 606, 608, respectively, corresponding to thetransmission pairing 502, 504, 602. The selection options 604, 606, 608may transmit a signal from the user device 104 to the transmissionpairing system 102 to initiate a transmission process to transmit secureinformation between the source and destination included in thetransmission pairing. The transmission pairings display the destinationto which secure information may be transmitted. Based on the destinationof a checking account, the transmission pairing 502 may correspond to atransfer type of transmission from one account held by the user to thechecking account also held by the user. Based on the destination of asewer utility company and a garbage utility company, the transmissionpairings 404, 602 may correspond to a payment type of transmission froman account held by the user to an account held by a third party.

FIG. 7 is an example of a user interface 700 displaying details 702corresponding to an executed transmission according to some aspects ofthe present disclosure. The transmission relates to a payment andincludes a destination of a corporate account (e.g., AA Travel). Thesource is a checking account held by the user. The transmission alsoincludes an instructive note (e.g., a “memo”) submitted with thetransmission. In some aspects, all or a portion of the transmissiondetails (e.g., the source and the destination) may be stored in thesecure database 120 as historical transmission data 208. The userinterface 700 includes a selection option 704 that may be selected bythe user to save the source and the destination of the transmission as atransmission pairing. In some aspects, the transmission pairing system102 may generate a transmission pairing using the source and thedestination from the executed transmission via the process described inblock 314.

Initiating a Transmission Using a Transmission Pairing

FIG. 8 is a flow chart of a process for implementing a transmissionusing a transmission pairing according to some aspects of the presentdisclosure. The process is described with respect to the networkenvironment 100 of FIG. 1 and the secure database 120 of FIGS. 1 and 2,although other implementations are possible without departing from thescope of the present disclosure.

In block 800, a selection of a transmission pairing is received. In someaspects, the selection is received by the transmission pairing system102 as a signal transmitted from the user device 104 in response to auser selection. For example, the transmission pairing system 102 maygenerate a user interface including one or more transmission pairings,as described in block 316 of FIG. 3. The transmission pairings may eachinclude a selection option corresponding to the transmission pairingthat may be selected by the user to initiate the transmission process.In response to selecting the selection option, the signal may betransmitted to the transmission pairing system 102.

In block 802, the transmission pairing system 102 generates a userinterface displaying the transmission pairing with an input option thatmay be selected by the user via the user device to input a parameter forthe transmission. In some aspects, the parameter may includealphanumeric text and be entered into the input option using a keyboardof the user device 104.

In block 804, a parameter is received. The parameter may be received bythe transmission pairing system 102 in response to a selection of theselection option and a response. The parameter may correspond to thesecure information to be transmitted from the source identified in thetransmission pairing to the destination identified in the transmissionpairing. The parameter may further correspond to a value or otherindication of how the secure information of the source should bemodified to account for the transmission at least a portion of thesecure information from the source to the destination.

In block 806, the transmission pairing system 102 determines if thetransmission pairing would result in a valid transmission. Thevalidation may take place in response to a user selecting a selectionoption to initiate the transmission. In some aspects, the validationprocess may include validating that that the transmission may beinitiated at the selected time. For example, the transmission pairingsystem 102 may determine whether conditions regarding the transmissionhave not changed since the transmission pairing was created or stored bythe system, such as, but not limited to whether accounts associated withthe source and destination still exist). The validation process may alsoinclude validating that the conditions are appropriate to initiate thetransmission at the time indicated. For example, in the case of thetransmission of monetary information, the system may validate that thedonor account includes sufficient funds to initiate a transfer based onthe inputted parameter. As another example, the system may validate thata transmission may be initiated on the particular date (e.g.,determining whether it is a national holiday or weekend). In additionalaspects, the validation process may include determining whether thesource is able to transmit secure information based on the parameterentered into the input option. For example, where the secure informationrelates to monetary information, the transmission pairing system 102 maydetermine whether the source has sufficient funds to allow for atransmission of the value identified as the parameter from the source tothe destination (e.g., whether an account associated with the source hasa sufficient balance).

In block 808, the transmission is initiated subsequent to adetermination that the transmission is valid. In some aspects, thetransmission pairing system 102 may initiate the transmission based onthe parameter inputted by the user. For example, the transmission mayinclude modifying the destination and source corresponding to theparameter. Returning to the example of transmitting monetaryinformation, the secure account information corresponding to the sourcemay be modified to subtract or withdraw a value or amount inputted asthe parameter by the user. The secure account information correspondingto the destination may be modified to add or deposit an amount inputtedas the parameter. The transmission may also be initiated based on thetransmission type associated with the transmission. The transmissionpairing system 102 may initiate a type-A transmission by causing theprocessor 110 to execute the Type-A instructions 116. The transmissionpairing system 102 may initiate a Type-B transmission by causing theprocessor 110 to execute the Type-B instructions 118.

In block 810, the transmission may not be initiated subsequent to adetermination that the transmission is invalid. In some aspects, thetransmission pairing system 102 may generate a user interface includingan error message or otherwise indicating that the transmission wasunsuccessful. In some aspects, the transmission pairing system 102 mayreturn the user to a process for regenerating a valid transmissionpairing using the process of FIG. 3.

Illustrative Example of Initiating a Transmission Using a TransmissionPairing

FIG. 9 is an example of a user interface 900 for implementing atransmission using a transmission pairing according to some aspects ofthe present disclosure. The user interface 900 may be generated inresponse to a selection of selection option corresponding to thetransmission pairing. For example, the user interface 900 may begenerated by the transmission pairing system 102 in response a userselecting the selection option 606 corresponding to the transmissionpairing 504 of FIG. 6. The user interface 900 includes details regardingthe transmission pairing, including the destination and the sourcestored in the secure database 120. The user interface 900 also includesan input option 904 that may be selected by the user via the user device104 to input a parameter. In the present example, the parametercorresponds to an amount of money. The user may select the input optionand enter a monetary amount using the keyboard of user device 104. Theuser interface 900 also includes a second input option 906 that allowsthe user to select a date or time for initiating the transmission. Insome aspects, availability of the input option 906 may depend on thetransmission type. For example, a payment-type transmission may includethe input option 906, but a transfer-type transmission may not. The usermay select the “Continue” selection option to submit the transmissionfor validation.

FIG. 10 is an example of a user interface 1000 confirming thetransmission of FIG. 9 according to some aspects of the presentdisclosure. The user interface 1000 may be generated in response to adetermination by the transmission pairing system 102 that thetransmission is valid. The user interface 1000 indicates that theparameter corresponded to a monetary value of $100. Secure informationmay be transmitted from the source (e.g., the checking account) to thedestination (e.g., the sewer utility company) corresponding to themonetary value. For example, the secure information may include anelectronic payment or an instruction causing the monetary value to beadded to the account associated with the destination and subtracted fromthe account associated with the source.

The foregoing description of the examples, including illustratedexamples, of the invention has been presented only for the purpose ofillustration and description and is not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Numerousmodifications, adaptations, and uses thereof will be apparent to thoseskilled in the art without departing from the scope of this invention.The illustrative examples described above are given to introduce thereader to the general subject matter discussed here and are not intendedto limit the scope of the disclosed concepts.

What is claimed is:
 1. A system comprising: a database; a processorcommunicatively coupleable to the database; and a memory includinginstructions that are executable by the processor for causing theprocessor to: transmit a first user interface to a user device of auser, the first user interface including input objects through which theuser can input a source account and a destination account for anelectronic monetary transfer, and the first user interface including aselectable object to initiate the electronic monetary transfer;detecting a selection of the selectable object in the first userinterface; in response to detecting the selection of the selectableobject, initiate the electronic monetary transfer between the sourceaccount and the destination account; in response to detecting acompletion of the electronic monetary transfer between the sourceaccount and the destination account, transmit a second user interface tothe user device, the second user interface including a graphical objectthat is selectable by the user for storing a transmission pairingassociated with the source account and the destination account in thedatabase; detect a selection of the graphical object in the second userinterface; based on detecting the selection of the graphical object,store the transmission pairing in the database by linking a sourceidentifier corresponding to the source account and a destinationidentifier corresponding to the destination account together in thedatabase; subsequent to storing the transmission pairing in thedatabase, receive a user input from the user device for displaying alist of transmission pairings previously stored in the database inrelation to the user, the list of transmission pairings including thetransmission pairing; and in response to receiving the user input,transmit a third user interface to the user device, the third userinterface including the list of transmission pairings and correspondingselection objects, each transmission pairing in the list including arespective source account that is linked to a respective destinationaccount in the database, wherein the corresponding selection objects areeach selectable for initiating a respective transmission process using acorresponding one of the transmission pairings on the list.
 2. Thesystem of claim 1, wherein the second user interface includes summaryinformation about the electronic monetary transfer.
 3. The system ofclaim 1, wherein the list of transmission pairings includes at least twotransmission pairings.
 4. The system of claim 1, wherein the memoryfurther includes instructions that are executable by the processor forcausing the processor to: detect a selection of a selection object fromamong the corresponding selection objects of the third user interface,the selection object corresponding to a particular transmission pairingin the list of transmission pairings; in response to detecting theselection of the selection object, determine a source financial accountand a destination financial account associated with the particulartransmission pairing; based on determining the source financial accountand the destination financial account, transmit a fourth user interfaceto the user device, the fourth user interface specifying the sourcefinancial account and the destination financial account, and the fourthuser interface including an input object through which the user caninput a monetary amount for another electronic monetary transfer betweensource financial account and the destination financial account; receive,via the fourth user interface, an input from the user for initiating atransfer of the monetary amount from the source financial account to thedestination financial account; and in response to receiving the input,initiate a transmission process for transferring the monetary amountfrom the source financial account to the destination financial account.5. The system of claim 1, wherein the memory further includesinstructions that are executable by the processor for causing theprocessor to: in response to detecting the selection of the graphicalobject in the second user interface, transmit a fourth user interface tothe user device, the fourth user interface including an input objectthrough which the user can input a note associated with the transmissionpairing; receive the note from the user via the fourth user interface;and associate the note with the transmission pairing in the database. 6.The system of claim 5, wherein the fourth user interface specifies thesource account and the destination account.
 7. The system of claim 1,wherein the source account and the destination account are financialaccounts that belong to the user.
 8. A method comprising: transmitting,by a processor, a first user interface to a user device of a user, thefirst user interface including input objects through which the user caninput a source account and a destination account for an electronicmonetary transfer, and the first user interface including a selectableobject to initiate the electronic monetary transfer; detecting, by theprocessor, a selection of the selectable object in the first userinterface; in response to detecting the selection of the selectableobject, initiating, by the processor, the electronic monetary transferbetween the source account and the destination account; in response todetecting a completion of the electronic monetary transfer between thesource account and the destination account, transmitting, by theprocessor, a second user interface to the user device, the second userinterface including a graphical object that is selectable by the userfor storing a transmission pairing associated with the source accountand the destination account in a database; detecting, by the processor,a selection of the graphical object in the second user interface; basedon detecting the selection of the graphical object, storing, by theprocessor, the transmission pairing in the database by linking a sourceidentifier corresponding to the source account and a destinationidentifier corresponding to the destination account together in thedatabase; subsequent to storing the transmission pairing in thedatabase, receiving, by the processor, a user input from the user devicefor displaying a list of transmission pairings previously stored in thedatabase in relation to the user, the list of transmission pairingsincluding the transmission pairing; and in response to receiving theuser input, transmitting, by the processor, a third user interface tothe user device, the third user interface including the list oftransmission pairings and corresponding selection objects, eachtransmission pairing in the list including a respective source accountthat is linked to a respective destination account in the database,wherein the corresponding selection objects are each selectable forinitiating a respective transmission process using a corresponding oneof the transmission pairings on the list.
 9. The method of claim 8,wherein the second user interface includes summary information about theelectronic monetary transfer.
 10. The method of claim 8, wherein thelist of transmission pairings includes at least two transmissionpairings.
 11. The method of claim 8, further comprising: detecting aselection of a selection object from among the corresponding selectionobjects of the third user interface, the selection object correspondingto a particular transmission pairing in the list of transmissionpairings; in response to detecting the selection of the selectionobject, determining a source financial account and a destinationfinancial account associated with the particular transmission pairing;based on determining the source financial account and the destinationfinancial account, transmitting a fourth user interface to the userdevice, the fourth user interface specifying the source financialaccount and the destination financial account, and the fourth userinterface including an input object through which the user can input amonetary amount for another electronic monetary transfer between sourcefinancial account and the destination financial account; receiving, viathe fourth user interface, an input from the user for initiating atransfer of the monetary amount from the source financial account to thedestination financial account; and in response to receiving the input,initiating a transmission process for transferring the monetary amountfrom the source financial account to the destination financial account.12. The method of claim 8, further comprising: in response to detectingthe selection of the graphical object in the second user interface,transmit a fourth user interface to the user device, the fourth userinterface including an input object through which the user can input anote associated with the transmission pairing; receive the note from theuser via the fourth user interface; and associate the note with thetransmission pairing in the database.
 13. The method of claim 12,wherein the fourth user interface specifies the source account and thedestination account.
 14. The method of claim 8, wherein the sourceaccount and the destination account are financial accounts that belongto the user.
 15. A non-transitory computer-readable medium comprisingprogram code that is executable by a processor for causing the processorto: transmit a first user interface to a user device of a user, thefirst user interface including input objects through which the user caninput a source account and a destination account for an electronicmonetary transfer, and the first user interface including a selectableobject to initiate the electronic monetary transfer; detecting aselection of the selectable object in the first user interface; inresponse to detecting the selection of the selectable object, initiatethe electronic monetary transfer between the source account and thedestination account; in response to detecting a completion of theelectronic monetary transfer between the source account and thedestination account, transmit a second user interface to the userdevice, the second user interface including a graphical object that isselectable by the user for storing a transmission pairing associatedwith the source account and the destination account in a database;detect a selection of the graphical object in the second user interface;and based on detecting the selection of the graphical object, store thetransmission pairing in the database by linking a source identifiercorresponding to the source account and a destination identifiercorresponding to the destination account together in the database. 16.The non-transitory computer-readable medium of claim 15, wherein thesecond user interface includes summary information about the electronicmonetary transfer.
 17. The non-transitory computer-readable medium ofclaim 15, further comprising program code that is executable by theprocessor for causing the processor to: subsequent to storing thetransmission pairing in the database, receive a user input from the userdevice for displaying a list of transmission pairings previously storedin the database in relation to the user, the list of transmissionpairings including the transmission pairing; and in response toreceiving the user input, transmit a third user interface to the userdevice, the third user interface including the list of transmissionpairings and corresponding selection objects, each transmission pairingin the list including a respective source account that is linked to arespective destination account in the database, wherein thecorresponding selection objects are each selectable for initiating arespective transmission process using a corresponding one of thetransmission pairings on the list.
 18. The non-transitorycomputer-readable medium of claim 17, wherein the list of transmissionpairings includes at least two transmission pairings.
 19. Thenon-transitory computer-readable medium of claim 17, further comprisingprogram code that is executable by the processor for causing theprocessor to: detect a selection of a selection object from among thecorresponding selection objects of the third user interface, theselection object corresponding to a particular transmission pairing inthe list of transmission pairings; in response to detecting theselection of the selection object, determine a source financial accountand a destination financial account associated with the particulartransmission pairing; based on determining the source financial accountand the destination financial account, transmit a fourth user interfaceto the user device, the fourth user interface specifying the sourcefinancial account and the destination financial account, and the fourthuser interface including an input object through which the user caninput a monetary amount for another electronic monetary transfer betweensource financial account and the destination financial account; receive,via the fourth user interface, an input from the user for initiating atransfer of the monetary amount from the source financial account to thedestination financial account; and in response to receiving the input,initiate a transmission process for transferring the monetary amountfrom the source financial account to the destination financial account.20. The non-transitory computer-readable medium of claim 19, wherein thefourth user interface includes an input object through which the usercan input a note associated with the transmission pairing, and furthercomprising program code that is executable by the processor for causingthe processor to: receive the note from the user via the fourth userinterface; and associate the note with the transmission pairing in thedatabase.